-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2.13.0 #242
Merged
Merged
Release 2.13.0 #242
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PEP-668 allows file systems to be labeled as 'externally managed'. Pip will see this label and refuse to install into any directory thusly labeled. The idea is to prevent pip from installing its packages into a directory that the operating system owns. To install files correctly, I utilize a virtual environment and install them into there. The PATH variable is modified to point first at this virtual environment. uwsgi is installed into this virtual environment and run out of there rather than being run from the operating system.
…9336 [chore] master -> develop from PR #239 (develop)
CASMCMS-8879: Fix build issue caused by PEP-668
The python virtual environment change should enable us to move ahead to later versions of Alpine 3 beyond 3.18. These later versions should not cause problems due PEP-668 because the resolution to CASMCMS-8879 fixed that issue. Pinning the version to 3.18 prevented us from encountering the PEP-668 problem because it pinned to a version of Alpine that did not introduce the issue.
CASMCMS-8879: Unpin the Alpine version from 3.18 back to 3
Update CHANGELOG.
jsl-hpe
approved these changes
Jan 10, 2024
mharding-hpe
approved these changes
Jan 10, 2024
mharding-hpe
added a commit
that referenced
this pull request
Feb 5, 2024
…-1704990572 [chore] master -> develop from PR #242 (relaese/2.13.0)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary and Scope
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.
Testing
List the environments in which these changes were tested.
Tested on:
Test description:
The build built in the pipeline. I installed it on a system and the operators worked.
Risks and Mitigations
Are there known issues with these changes? Any other special considerations?
Pull Request Checklist